Pre-authorized transfer

ABSTRACT

Various examples described herein are directed to systems and methods that provide a pre-authorized amount from a user to an intended recipient that is remote from the user. A quick response (QR) code provided from a recipient is read. The QR code includes the pre-authorized amount to be withdrawn from an account associated the user and image data associated with the intended recipient. Image data associated with the recipient is captured. Image analysis is performed on the captured image data associated with the recipient. The analyzed captured image data associated with the recipient is compared with the image data associated with the intended recipient. A determination is then made if the recipient is the intended recipient based on the comparison. When the recipient is the intended recipient, the pre-authorized amount is provided to the recipient from the account associated with the user.

BACKGROUND

Occasionally, a user may need to provide money to a recipient in a shortperiod of time. As an example, a parent may need to provide their childwith money in order to allow the child to make an immediate purchase,such as money for books when their child is at school. In this scenario,there are a number of ways for the parent to provide money to theirchild. The parent can physically withdraw the money from their accountat an automated teller machine (ATM), at a branch of a bank, or a bankkiosk. Afterwards, the parent can physically provide the money to theirchild. In addition, the child can accompany the parent to the ATM, thebank branch, or the bank kiosk in order to receive the money when theparent withdraws the money from their account. In either event, theparent must be located proximate with their child in order to affect thetransfer of money from their account to the child. Further, the parentmay wire money to their child using various money wire services orapplications. However, using these services incurs fees.

SUMMARY

Therefore, what is needed is technical solution that provides a systemand method and solves the technical problems of allowing a user toprovide money to a recipient from an account associated with the userwithout requiring the user to be located proximate to the recipient.Moreover, the system and method should provide the technical solution ofallowing the user to affect the transfer to the recipient without usinga third party and incurring wiring fees associated with the third partyby allowing the recipient to directly withdraw the money from theaccount of the user.

Embodiments solve the problems noted above by providing a system andmethod of allowing a user to pre-authorize an intended recipient towithdraw money from an account associated with the user at a locationremote from a location of the user. In an embodiment, a user maypre-authorize an intended recipient to withdraw money from a useraccount associated with the user at a location that is remote from theuser. The intended recipient otherwise lacks access to the accountassociated with the user, in an embodiment, the user can indicate anamount the intended recipient is authorized to withdraw from the useraccount along with identification (ID) data associated with the intendedrecipient. The ID data can be an image of the intended recipient. Theamount the intended recipient is authorized to withdraw along with theID data is used to generate a quick response (QR) code. In anembodiment, the user can forward the QR code to the intended recipient.When the intended recipient desires to access the user account, theintended recipient presents the QR code. Moreover, ID data associatedwith the intended recipient is captured at the location where theintended recipient is attempting to withdraw the money. In anembodiment, the location where the intended recipient is attempting towithdraw the money is remote from a location of the user associated withthe user account.

The ID data captured at the location where the intended recipient isattempting to withdraw the money is analyzed and compared with the IDdata provided by the user associated with the user account using imageanalysis. If the captured ID data matches the ID data provided by theuser, the intended recipient is able to withdraw the money from the useraccount. Moreover, the user is informed of the successful withdrawal.

If the captured ID data does not match the ID data provided by the userassociated with user account, an alert is sent to the user. The alertcan indicate to the user that a withdrawal was attempted using the QRcode. Moreover, the alert can include the captured ID data. In anembodiment, the user can examine the captured ID data and authorize thewithdrawal based on the captured ID data.

BRIEF DESCRIPTION OF FIGURES

FIG. 1 shows an environment in which embodiments of the presentdisclosure may operate.

FIGS. 2A and 2B illustrate a process flow for allowing a user topre-authorize withdrawal of money from a user account associated with auser according to an embodiment of the present disclosure.

FIG. 3 illustrates a UI that provides an internet banking applicationaccording to an embodiment of the present disclosure.

FIG. 4 illustrates a UI that prompts a user to capture ID data accordingto an embodiment of the present disclosure.

FIG. 5 illustrates capturing ID data for an intended recipient accordingto an embodiment of the present disclosure.

FIG. 6 shows a QR code that includes data corresponding to apre-authorized amount that can be withdrawn from a user account alongwith ID data associated with an intended recipient according to anembodiment of the present disclosure.

FIG. 7 illustrates a money dispensing machine reading the QR code ofFIG. 6 and capturing ID data of a recipient according to an embodimentof the present disclosure.

FIGS. 8A-8E describe a process flow for allowing a user to pre-authorizewithdrawal of money from a user account associated with a user and thenallow withdrawal of the pre-authorized amount when captured ID data doesnot match ID data in a QR code, in accordance with an embodiment of thepresent disclosure.

FIG. 9 illustrates an alert, such as a UI, that can be sent to a userdevice when captured ID data associated with a pre-authorized withdrawaldoes not match ID associated with an intended recipient, in accordancewith an embodiment of the present disclosure.

FIG. 10 shows a UI that includes an image of a recipient who attemptedto withdraw money pursuant to a pre-authorized withdrawal along withoptions for responding to the attempted withdrawal, in accordance withan embodiment of the present disclosure.

FIG. 11 is a block diagram showing one example of a softwarearchitecture for a computing device, in accordance with an embodiment ofthe present disclosure.

FIG. 12 is a block diagram illustrating a computing device hardwarearchitecture, within which a set or sequence of instructions can beexecuted to cause the machine to perform examples of any one of themethodologies discussed herein, in accordance with an embodiment of thepresent disclosure.

DETAILED DESCRIPTION

Now making reference to the Figures, and more specifically FIG. 1 , anenvironment 100 is shown in which embodiments of the present solutionmay operate. The environment 100 can include a server 102 incommunication with user devices 104 and a network 106. Via the network106, the server 102 communicates with the user devices 104 and providesuser interfaces (UIs) 108 for display on the user devices 104. Moreover,the server 102 communicates with a recipient device 110 via the network106.

As will be discussed in greater detail below, each of the server 102,the user devices 104, and the recipient device 110 may incorporate anarchitecture that facilitates operation in the capacity of either aserver of a client machine in server-client network environments, whereeach of these devices may be implemented as any type of computingdevice, such as a server computer, a personal computer (PC), or the likeeach having a processor configured to perform the subject matterdisclosed herein. The server 102, the user devices 104, and therecipient device 110 may be any computing device suitable for use by auser. For example, the devices may be a desktop computer, a tabletcomputer, a portable media device, or a smart phone belonging to a user.Throughout this disclosure, reference may be made to a user device 104and user devices 104. It should be pointed out that the term “userdevice 104” is interchangeable with the term “user devices 104.” Thus,any description for the user device 104 is applicable to the userdevices 104. Likewise, any description for the user devices 104 isapplicable to the user device 104.

The network 106 may be any network that enables communication between oramong machines, databases, and devices (e.g., the server 102, the userdevices 104, and the recipient device 110). Accordingly, the network 106may be a wired network, a wireless network (e.g., a mobile or cellularnetwork), or any suitable combination thereof. The network 106 mayinclude one or more portions that constitute a private network, a publicnetwork (e.g., the Internet), or any suitable combination thereof.Accordingly, the network 106 may include one or more portions thatincorporate a local area network (LAN), a wide area network (WAN), theInternet, a mobile telephone network (e.g., a cellular network), a wiredtelephone network (e.g., a plain old telephone system (POTS) network), awireless data network (e.g., WiFi network or WiMax network), or anysuitable combination thereof. Any one or more portions of the network106 may communicate information via a transmission medium. As usedherein, “transmission medium” shall be taken to include any intangiblemedium that is capable of storing, encoding, or carrying instructionsfor execution by a machine, and includes digital or analog communicationsignals or other intangible media to facilitate communication of suchsoftware.

The user devices 104 and the recipient device 110 can be any computingdevice suitable for use by a user. For example, the user devices 104 canbe a desktop computer, a tablet computer, a portable media device, or asmart phone belonging to a user. The UIs 108 can be a graphical userinterface that allows a user to directly interact with electronicdevices, such as the user devices 104 and the recipient device 110,through graphical elements, such as icons, and/or audio indicators,where the actions in the UIs 108 are performed through directmanipulation of the graphical elements. In addition, the UIs 108 arecapable of displaying information received from a user on the userdevices 104. Throughout this disclosure, reference may be made to a UI108 and UIs 108, It should be pointed out that the term “UI 108” isinterchangeable with the term “UIs 108.” Thus, any description for theUI 108 is applicable to the UIs 108. Similarly, any description for theUIs 108 is applicable to the UI 108.

As noted above, embodiments provide a system and method of allowing auser to pre-authorize an intended recipient to withdraw money from anaccount associated with the user at a location remote from a location ofthe user. In an embodiment, the user can indicate an amount the intendedrecipient is authorized to withdraw from the user account along with IDdata associated with the recipient. The amount the intended recipient isauthorized to withdraw along with the ID data is used to generate a QRcode. In an embodiment, the user can forward the QR code to the intendedrecipient. When the intended recipient desires to access the useraccount to withdraw the pre-authorized amount, the intended recipientpresents the QR code. Moreover, ID data associated with the recipient iscaptured at the location where the recipient is attempting to withdrawthe money in order to confirm that the recipient is the intendedrecipient, e.g., the person presenting the QR code at a money dispensingmachine is actually the recipient the user associated with the useraccount intended to receive the money. FIGS. 2A and 2B illustrate aprocess flow for allowing a user to pre-authorize withdrawal of moneyfrom a user account associated with a user. It should be noted thatwhile money is described as an item to be withdrawn from a user accountby an intended recipient different from a user associated with the useraccount, embodiments envision any type of instrument or verifiablerecord that is accepted as payment for goods and services.

Now making reference to FIG. 2A, in an operation 200, an indication topre-authorize a withdrawal from an account associated with a user isreceived at the user device 104. In an embodiment, at the user device104, a user can be provided with the UI 108 on the user device 104during the operation 200. The UI 108 can be any type of internet bankingapplication or digital wallet that allows for electronic access to useraccounts that hold money. Moreover, the UI 108 can be any type ofinternet banking application or digital wallet that allows a user tomake electronic transactions with another user. As shown with referenceto FIG. 3 , the UI 108 can include a checkbox 300 that provides the userwith an option to select a pre-authorization withdrawal. In particular,the user may engage the checkbox 300 with an “X,” as shown, or any othertype of indicia, such as a check mark, signature, initials, etc. Whenthe user engages the checkbox 300, the user device 104 receives theindication to pre-authorize a withdrawal. In an embodiment, with the UI108, a user can allow for an intended recipient to withdraw money from auser account associated with the user. In an embodiment, the intendedrecipient lacks access to the user account, e.g., the intended recipientis not authorized to access the user account or is not associated withthe user account. As such, the intended recipient cannot otherwiseaccess the user account. Thus, instead of the user having to transferthe money to an account associated with the intended recipient, whichmay be time consuming and incur fees, the user can allow for an intendedrecipient to directly withdraw money from the user account associatedwith the user.

To further illustrate, in an example, referred to herein as thefather/daughter example, a daughter, who is currently located inMinnesota and attending school in Minneapolis, may need to purchasebooks that cost $500. Thus, the daughter asks her father, who is locatedin North Carolina, for $500. In the father/daughter example, the fatheris the user and the daughter is the intended recipient. Moreover, thedaughter otherwise lacks access to the account associated with thefather, i.e., the daughter cannot access a user account associated withthe father. In the father/daughter example, in order to allow thedaughter to withdraw the money directly from the user account associatedwith the father, the father accesses the internet banking applicationdisplayed on the UI 108 on the user device 104 associated with thefather. During the operation 200, the father checks the checkbox 300 inthe UI 108 such that the user device 104 associated with the fatherreceives an indication to pre-authorize a withdrawal from the useraccount associated with the father. After the user device 104 receivesan indication to pre-authorize a withdrawal from a user account, themethod performs an operation 202, as shown with reference to FIG. 2A.

In the operation 202, an amount that is pre-authorized for withdrawal isreceived at the user device 104. In an embodiment, the user may enter anamount at an input field 302 of the UI 108, as shown with reference toFIG. 3 . It should be noted that a user may input any amount at theinput field 302. Returning to the father/daughter example, as notedabove, the daughter needs $500 to cover the costs associated withpurchasing hooks. Thus, during the operation 202, the father enters $500at the input field 302, as shown with reference to FIG. 3 . When thefather inputs $500 at the input field 302, the user device 104associated with the father receives the pre-authorized amount of $500 inthe operation 202.

Returning attention to FIG. 2A, when the user decides to pre-authorize awithdrawal, the UI 108 can prompt the user to provide ID data associatedwith the intended recipient in order to allow the user device 104 toreceive ID data associated with the intended recipient during anoperation 204. In an embodiment, the UI 108 provides a selector 304 thatrequests the user click on the selector 304 to provide the ID dataduring an operation 204. The ID data may be any type of data, such asbiometric data, that is unique to the intended recipient and can be usedto identify the intended recipient for security purposes, Examples of IDdata can include an image of the intended recipient, a fingerprint ofthe intended recipient, retinal scanning data, or any other type ofidentifying data that is capable of being captured and transferred usingany type of electronic circuitry. In an embodiment, when the userengages the selector 304, such as by clicking on the selector 304, a UI400 is presented on the user device that includes a prompt 402, as shownwith reference to FIG. 4 . The prompt 402 requests that the user eithercapture image data associated with the intended recipient or provideimage data associated with the intended recipient. For example, a cameraof the user device 104 may automatically be accessed when the selector304 is engaged and after the prompt 402 is displayed. In an embodiment,using a camera of the user device 104, the user may capture image dataassociated with an image of the intended recipient. In an embodiment,the image data can be the ID data that is received by the user device104 during the operation 204. In alternative embodiments, the user canhave ID data pre-stored at the user device 104. To further illustrate,the user can have images of the intended recipient that were captured inthe past stored on the user device 104. These previously captured imagescan be provided as the ID data during the operation 204.

In the father/daughter example, after the father enters $500 at theinput field 302, the father clicks on the selector 304 and the UI 400 ispresented that prompts the father to either capture image dataassociated with the daughter or provide image data associated with thedaughter via the prompt 402. Thus, during the operation 204, the fathercaptures an image 500 (FIG. 5 ) having image data 502 of his daughterwith a camera 504 of the user device 104. In the example, the image data502 can correspond to the ID data associated with the daughter.

Returning attention to FIG. 2A and the process flow for allowing a userto pre-authorize withdrawal of money from a user account associated witha user, after the user device 104 receives the pre-authorized amount andthe ID data in the operations 202 and 204, the user device 104 sends thepre-authorized amount and the ID data to the server 102 during anoperation 206. In an alternative embodiment, the user device 104 canalso send identification information associated with the user device 110of the intended recipient along with the pre-authorized amount and theID date in the operation 206. The identification information can includea phone number associated with the user device 110 of the intendedrecipient, a social media address associated with the intendedrecipient, or any other type of contact information that can be used toconvey electronic information, such as QR codes, to the intendedrecipient.

When the server 102 receives the pre-authorized amount and the ID data,the server 102 can generate a QR code during an operation 208. The QRcode generated by the server 102 can store the pre-authorized amountalong with the ID data. Thus, when the QR code is read, in anembodiment, a device associated with the reader can determine the amountthe user of the QR code is authorized to withdraw from the user accountusing any suitable techniques known to those skilled in the art.Moreover, when the QR code is read, the device associated with thereader can determine the ID data that can be used to verify the personproviding the QR code is the intended recipient using any suitabletechniques known to those skilled in the art.

In an embodiment, the server 102 can create any type of QR code, such asan IQR code, a secure QR code, a frame QR, a High Capacity Colored2-Dimensional, or the like, using any well-known, suitable techniquesknown to those skilled in the art during the operation 208. For example,the QR code can be created using any well-known QR code generator thatuses application programming interfaces to automatically fuse and encodedata into graphic designs. Examples include QRTiger, QRSTUFF™, QRD.BY,Visualead™, FORQR, or the like. After creating the QR code, the server102 can forward the QR code to the user device 104 during an operation210. Optionally, the server 102 can forward the QR code to the userdevice 110. In the father/daughter example, the user device 104associated with the father sends the pre-authorized amount of $500 andthe ID data associated with his daughter to the server during theoperation 206. During the operation 208, the server 102 creates a QRcode 600 (FIG. 6 ) and sends the QR code 600 to the user device 104during the operation 210.

Returning to FIG. 2A, after the user device 104 receives the QR codeduring the operation 210, the user device sends the QR code to the userdevice 110 associated with the intended recipient during an operation214. Once the user device 110 receives the QR code, the intendedrecipient associated with the user device 110 can present the QR code toa money dispensing machine 112, such as an ATM, during an operation 216.In the father/daughter example, from the user device 104, the fathersends the QR code 600 to the user device 110 associated with thedaughter in Minneapolis while the father is located in North Carolina.The daughter then presents the QR code 600 to the money dispensingmachine 112 that is located in Minnesota during the operation 216.

The money dispensing machine 112 can include a camera that reads the QRcode. Thus, the money dispensing machine 112 can read the QR code duringan operation 218 when the recipient presents the QR code, as shown withreference to FIG. 2A. Based on the QR code, the money dispensing machine112 can determine the pre-authorized amount of money to withdraw fromthe user account of the user associated with the user device 104 duringan operation 220. Moreover, based on the QR code, during an operation222, the money dispensing machine 112 can glean the ID data associatedwith the intended recipient and determine that ID data of the recipientassociated with the user device 110 should be captured.

During an operation 224, the money dispensing machine 112 captures IDdata of the recipient associated with the user device 110. To furtherillustrate, in instances where the ID data includes an image of theintended recipient, the money dispensing machine 112 can capture animage of the person associated with the user device 110 using the moneydispensing machine camera. In instances where the ID data includes afingerprint of the intended recipient, the money dispensing machine 112can include a fingerprint reader to read the fingerprint of therecipient associated with the user device 110. Furthermore, in instanceswhere the ID date includes retinal scanning data, the money dispensingmachine can include a retinal scanner to capture ID data of therecipient associated with the user device 110.

Regardless of the type of ID data, once the money dispensing machine 112captures the ID data during the operation 224, the money dispensingmachine 112 analyzes the captured ID data during an operation 225 anddetermines that the ID data captured during the operation 224 matchesthe ID data gleaned from the QR code during an operation 226. Thus, themoney dispensing machine 112 can determine that the recipient associatedwith the user device 110 that presented the QR code during the operation216 is the intended recipient. To further illustrate, the moneydispensing machine 112 can perform an image analysis on the captured IDdata and compare the image analysis with the ID data gleaned from the QRcode during the operation 225. In this illustration, the moneydispensing machine 112 can use digital image processing techniques toextract information from the captured image. The money dispensingmachine 112 can employ pattern recognition, digital geometry, signalprocessing during digital image processing, or the like. Examples oftechniques that can be used include 2D and 3D object recognition, imagesegmentation, single particle tracking, optical flow, 3D PoseEstimation, or any other suitable techniques. In an embodiment, afterthe money dispensing machine 112 performs image analysis on the capturedID data, the money dispensing machine can compare the analyzed capturedID data with the ID data gleaned from the QR code and determine, basedon the comparison, that the captured ID data matches the ID data gleanedfrom the QR code, during the operation 226.

In alternative embodiments, after the money dispensing machine 112captures the ID data during the operation 224, the money dispensingmachine 112 can forward the captured ID data and the QR code to theserver 102 during an operation 228. In an embodiment, the server 102 candetermine that the captured ID data matches the ID data gleaned from theQR code as discussed above during operations 229 and 230, using thetechniques discussed above with reference to the operations 225 and 226.Upon determining a match, the server 102 can provide authorization tothe money dispensing machine 112 to dispense the pre-authorized amountto the recipient in an operation 232. Once a determination is made thatthe recipient associated with the user device 110 is the intendedrecipient, the money dispensing machine 112 provides the recipientassociated with the user device 110 with the pre-authorized amount.

Returning to the father/daughter example, during the operation 216, thedaughter presents the QR code 600 to the money dispensing machine 112,as shown with reference to FIG. 7 . In the operation 218, a camera 700of the money dispensing machine 112 reads the QR code 600. The moneydispensing machine 112 then determines that the pre-authorized amount towithdraw from the user account associated with the father is $500 duringthe operation 220 based on the QR code 600. In addition, the moneydispensing machine 112 determines the image data 502, which cancorrespond to the ID data, associated with the intended recipient, whichin the father/daughter example is the daughter, by gleaning thisinformation from the QR code 600 during the operation 222. In responseto reading the QR code 600, the money dispensing machine 112 uses thecamera 700 to capture ID data associated with the daughter during theoperation 224.

In the father/daughter example, after capturing the ID data associatedwith the daughter, the money dispensing machine 112 performs imageanalysis on the captured ID data, compares the analyzed data with the IDdata gleaned from the QR code 600, and determines that the analyzed datamatched the ID data gleaned from the QR code 600 during the operation226. Thus, the money dispensing machine 112 determines that the daughteris the intended recipient and dispenses $500.

After the money dispensing machine 112 dispenses the $500, the moneydispensing machine 112 provides an acknowledgment of the withdrawal tothe server 102 during an operation 236. Moreover, in an embodiment, whenthe money dispensing machine 112 provides the acknowledgement of thewithdrawal to the server 102, this causes the server 102 to send anacknowledgement of the withdrawal to the user device 104 that includesan image of the recipient indicating that the pre-authorized amount waswithdrawn from the user account associated with the user of the userdevice 104 during an operation 238. Additionally, the QR codeautomatically expires after withdrawal of the pre-authorized amount. Inthe father/daughter example, after the money dispensing machine 112dispenses the $500, the money dispensing machine 112 sends anacknowledgement of the withdrawal that includes an image of the daughterto the server 102 during the operation 236. The server 102 then sends anacknowledgement of the withdrawal to the father by sending theacknowledgement of withdrawal that includes an image of the daughter tothe user device 104 associated with the father during the operation 238.

In the embodiment discussed above with reference to FIGS. 2A and 2B,during the operations 226 and 230, a determination was made that thecaptured ID data matched the ID data gleaned from the QR code, Thus, theintended recipient was provided the pre-authorized amount during theoperation 234. In an alternative embodiment, when the ID data iscaptured, a match may not be found between the captured ID data and thedata gleaned from the QR code. However, in an alternative embodiment,the pre-authorized amount may still be provided, as described withreference to FIGS. 8A-8C, which describe a process flow for allowing auser to pre-authorize withdrawal of money from a user account associatedwith a user and then allow withdrawal of the pre-authorized amount whencaptured ID data does not match ID data in a QR code.

Now making reference to FIG. 8A, the process flow includes theoperations 200-224 and 228. The operations 200-224 and 228 shown withreference to FIG. 8A are the same as the operations 200-224 and 228discussed in detail with reference to FIGS. 2A and 2B. Therefore,discussion will be omitted for the operations 200-224 and 228 shown withreference to FIGS. 8A and 8B. Instead, discussion will begin withoperation 800. During the operation 800, after the money dispensingmachine 112 has captured ID data of the user presenting the QR cardduring the operation 224 and analyzed the captured ID data, the moneydispensing machine 112 can perform an image analysis on the captured IDdata and compare the image analysis with the ID data gleaned from the QRcode using the techniques discussed above. However, in this embodiment,during the operation 800, the money dispensing machine 112 can determinethat the captured ID data does not match ID data gleaned from the QRcode. It should be pointed out that in addition to the money dispensingmachine 112 making the determination during the operation 800,alternatively, the server 102 can determine that the captured ID datadoes not match ID data gleaned from the QR code in a manner similar tothe money dispensing machine 112 during an operation 802, In anembodiment, the server 102 can make this determination after the server102 analyzes the captured ID data during the operation 229 using thetechniques described above.

When the money dispensing machine 112 determines that the captured IDdata does not match the ID data gleaned from the QR code during theoperation 800, the money dispensing machine 112 sends a message to theserver 102 along with the captured ID data indicating that the capturedID data does not match the ID data gleaned from the QR code during anoperation 804, as shown with reference to FIG. 8C. In an operation 806,the server 102 sends an alert to the user device 104, which displays thealert along with the captured ID data during an operation 808.

As an example of a process flow for allowing a user to pre-authorizewithdrawal of money from a user account associated with a user whencaptured ID data does not match ID data in a QR code, again, a daughterwho is currently located in Minnesota and attending school inMinneapolis may need to purchase books that cost $500. Thus, thedaughter asks her father, who is located in North Carolina, for $500.For the purposes of the disclosure, this example will be referred to asthe second father/daughter example. In the second father/daughterexample, the operations 200-224 are performed as described above withreference to FIGS. 2A-6 . However, during the operation 800, when themoney dispensing machine camera 700 captures the image of the daughter,the daughter is wearing glasses (FIG. 10 ). Thus, during the operation800, the money dispensing machine 112 determines that the captured IDdata does not match the ID data gleaned from the QR code. Accordingly,the money dispensing machine 112 sends a message to the server 102indicating that captured ID data does not match the ID data gleaned fromthe QR code during the operation 804. In the second father/daughterexample, the server 102 sends an alert to the user device 104 associatedwith the father, which then displays an alert 900, as shown withreference to FIG. 9 , during the operation 808. As may be seen withreference to FIG. 9 , the alert 900 can include a message 902 thatindicates incorrect ID data was received with the pre-authorizationrequest. In an embodiment, the alert 900 can be a UI presented on theuser device 104 associated with the father.

Returning attention to FIG. 8C and the process flow for allowing a userto pre-authorize withdrawal of money from a user account associated witha user when captured ID data does not match ID data in a QR code, afterthe alert is displayed at the user device 104 in the operation 808, theuser associated with the user device 104 and the user account from whichthe pre-authorized withdrawal was attempted can engage the alertdisplayed on the user device 104. The user associated with the userdevice 104 can engage the alert by tapping the alert or engaging thealert by some other well-known means such that the user device 104receives an engagement of the alert during an operation 810. When thealert is engaged, a UI 1000 is displayed on the device 104, as shownwith reference to FIG. 10 during an operation 812. Now making referenceto FIG. 10 , the UI 1000 includes an image 1002 of the recipient whoattempted to withdraw the money pursuant to the pre-authorizedwithdrawal. In addition, the UI 1000 includes options 1004 and 1006. Theoption 1004 allows the user associated with the user account to allowthe withdrawal. In particular, the user associated with the user accountmay select checkbox 1008, which allows the pre-authorized withdrawal toproceed. Alternatively, if the user associated with the user accountselects checkbox 1010, the pre-authorized withdrawal request is denied.

In an embodiment, when the user associated with the user account decidesto allow the pre-authorized withdrawal to proceed, the process flowmoves to FIG. 8D and an operation 814 is performed, where a selection ofthe checkbox 1008, which is a selection authorizing the withdrawal, isreceived. When the selection authorizing the withdrawal is receivedduring the operation 814, the user device 104 sends an authorization toallow the pre-authorized transaction to proceed to the server 102 duringan operation 816. During an operation 818, the server 102 sends anauthorization to allow the pre-authorized transaction to proceed to themoney dispensing machine 112. In response to receiving the authorizationduring the operation 818, the money dispensing machine 112 provides thepre-authorized amount to the recipient associated with the user device110 who requested the pre-authorized withdrawal during an operation 820.Furthermore, after the money dispensing machine 112 provides thepre-authorized amount to the recipient, the money dispensing machine 112provides an acknowledgment of the withdrawal to the server 102 during anoperation 824. Moreover, sending the acknowledgment of the withdrawal tothe server 102 causes the server 102 to send an acknowledgement of thewithdrawal to the user device 104 indicating that the pre-authorizedamount was withdrawn from the user account associated with the user ofthe user device 104 during an operation 826. In an embodiment, theacknowledgement sent during the operation 826 can include the ID datacaptured by the money dispensing machine 112. Furthermore, the QR codeautomatically expires after withdrawal of the pre-authorized amount.

In an alternative embodiment, when the user associated with the useraccount decides to deny the pre-authorized withdrawal, the process flowmoves to FIG. 8E and an operation 828 is performed, where a selection ofthe checkbox 1010, which is a selection denying the withdrawal, isreceived. When the selection denying the withdrawal is received duringthe operation 828, the user device 104 sends a denial of the withdrawalto the server 102 during an operation 830. During an operation 832, theserver 102 sends a denial of the withdrawal to the money dispensingmachine 112. In response to receiving the denial during the operation832, the money dispensing machine 112 sends a denial to the recipientassociated with the user device 110 who requested the pre-authorizedwithdrawal during an operation 834, Furthermore, after the moneydispensing machine 112 sends the denial to the recipient associated withthe user device 110, the money dispensing machine 112 sends anacknowledgment of the denial to the server 102 during an operation 836.Moreover, upon receiving the denial, the server 102 sends anacknowledgement of the denial to the user device 104 indicating that thepre-authorized amount was denied during an operation 838.

Returning to the second father/daughter example, in this example, in theimage 500 of the daughter that was the ID data provided during theoperation 204, the daughter is not wearing glasses. However, when themoney dispensing machine camera 700 captures an image of the daughterduring the operation 224, the daughter is wearing glasses. Thus, duringthe operation 800, the money dispensing machine 112 determines that thecaptured ID data does not match the ID data gleaned from the QR code.Accordingly, the money dispensing machine 112 sends a message along withthe captured ID data to the server 102 indicating that the ID data doesnot match during the operation 804. In response, the server 102 sends analert to the user device 104 associated with the father during theoperation 806. In the second father/daughter example, the UI 1000 isdisplayed on the user device 104 associated with the father. The UI 1000includes the image 1002, which shows his daughter wearing glasses 1011.In response to seeing the image 1002 that shows his daughter wearing theglasses 1011, the father selects the option 1004 by placing an indicia1012, such as an “X,” in the checkbox 1008. Thus, during the operation814, the user device 104 receives a selection authorizing the withdrawalduring the operation 814.

Upon receiving the authorization, the user device 104 sends anauthorization to allow the pre-authorized transaction to proceed to theserver 102 during the operation 816. In response to receiving theauthorization, in the second father/daughter example, the server 102sends an authorization to allow the pre-authorized transaction toproceed to the money dispensing machine 112 during the operation 818. Inresponse to receiving the authorization during the operation 818, themoney dispensing machine 112 provides $500 to the daughter during theoperation 820. Furthermore, after the money dispensing machine 112dispenses $500 to the daughter, the money dispensing machine 112provides an acknowledgment of the withdrawal to the server 102 duringthe operation 824. Moreover, upon receiving the acknowledgement of thewithdrawal, the server 102 sends an acknowledgement of the withdrawal tothe father indicating that $500 was withdrawn from the user accountassociated with the father during the operation 826.

As discussed above, embodiments provide a system and method that allowsa user to pre-authorize a withdrawal from an account associated with auser. Therefore, a user can provide money directly from an accountassociated with the user to a recipient who lacks access to the accountwithout having to physically be present with the recipient. Thus, theuser may be at a first location while the recipient is at a secondlocation separate and remote from the first location. Moreover, therecipient is able to withdraw money directly from the user accountassociated with the user. Thus, the user does not have to transfer fundsfrom the account associated with the user to an account associated witha recipient, thereby avoiding transactional costs, such as fees andtime. In addition, the user does not have to provide any type ofpersonal security information to the recipient, such as a personalidentification number, or any other security indicia that the user wouldprefer to keep private.

In addition, the user of a QR code along with the ID data, such as imagedata, adds two levels of security. In particular, the QR code is onelevel of security while the ID data is a second level of security.Moreover, when the image data captured at a money machine does not matchthe image data gleaned from a QR code, instead of denying the withdrawalrequest outright, the incorrect match is sent to the user associatedwith the user account from which the money is being withdrawn. Thus, theuser can determine if the recipient attempting to receive the money isin fact the intended recipient. In further embodiments, even when thecaptured ID data matches the ID data gleaned from the QR code, the imagedata can be sent to the user associated with the user account from whichthe money is being withdrawn. In an embodiment, this can serve as athird layer of security.

In a further embodiment, the user can make the QR code recurring over agiven time period. To further illustrate, in the father/daughterexample, the daughter may need to purchase books every semester. In anembodiment, the QR code can automatically be generated at the beginningof every semester and presented to the father. The father can thenforward along the automatically generated QR code to the daughter.Alternatively, upon automatic generation, the QR code can automaticallybe sent to both the father and the daughter. It should be pointed outthat after the user provides the ID data associated with the recipientas discussed above, the processes described herein can be performedwithout the involvement of any users, such as the father and/or thedaughter in the examples described above,

FIG. 11 is a block diagram 1100 showing one example of a softwarearchitecture 1102 for a computing device. The architecture 1102 may beused in conjunction with various hardware architectures, for example, asdescribed herein. FIG. 11 is merely a non-limiting example of a softwarearchitecture 1102 and many other architectures may be implemented tofacilitate the functionality described herein. The software architecture1102 may be executed on hardware such as, for example, any of thesystems or subsystems described herein. A representative hardware layer1104 is illustrated and can represent, for example, any of the abovereferenced computing devices. In some examples, the hardware layer 1104may be implemented according to the architecture 1102 of FIG. 11 and/orthe architecture 1200 of FIG. 12 .

The representative hardware layer 1104 comprises one or more processingunits 1106 having associated executable instructions 1108. Executableinstructions 1108 represent the executable instructions of the softwarearchitecture 1102, including implementation of the methods, systems,components, and so forth of FIGS. 1, 2A, 2B, and 8A-8E. Hardware layer1104 also includes memory/storage modules/data storage 1110, which alsohave executable instructions 1108. Hardware layer 1104 may also compriseother hardware as indicated by other hardware 1112 which represents anyother hardware of the hardware layer 1104, such as the other hardwareillustrated as part of hardware architecture 1200.

In the example architecture of FIG. 11 , the software architecture 1102may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 1102may include layers such as an operating system 1114, libraries 1116,frameworks/middleware 1118, applications 1120 and a presentation layer1122. Operationally, the applications 1120 and/or other componentswithin the layers may invoke application programming interface (API)calls 1124 through the software stack and receive a response, returnedvalues, and so forth illustrated as messages 1126 in response to the APIcalls 1124. The layers illustrated are representative in nature and notall software architectures have all layers. For example, some mobile orspecial purpose operating systems may not provide aframeworks/middleware layer 1118, while others may provide such a layer.Other software architectures may include additional or different layers.

The operating system 1114 may manage hardware resources and providecommon services. The operating system 1114 may include, for example, akernel 1128, services 1130, and drivers 1132. The kernel 1128 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 1128 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1130 may provideother common services for the other software layers. In some examples,the services 1130 include an interrupt service. The interrupt servicemay detect the receipt of a hardware or software interrupt and, inresponse, cause the architecture 1102 to pause its current processingand execute an interrupt service routine (ISR) when an interrupt isreceived. The ISR may generate the alert, for example, as describedherein.

The drivers 1132 may be responsible for controlling or interfacing withthe underlying hardware. For instance, the drivers 1132 may includedisplay drivers, camera drivers, Bluetooth® drivers, flash memorydrivers, serial communication drivers (e.g., Universal Serial Bus (USB)drivers), Wi-Fi® drivers, NFC drivers, audio drivers, power managementdrivers, and so forth depending on the hardware configuration.

The libraries 1116 may provide a common infrastructure that may beutilized by the applications 1120 and/or other components and/or layers.The libraries 1116 typically provide functionality that allows othersoftware modules to perform tasks in an easier fashion than to interfacedirectly with the underlying operating system 1114 functionality (e.g.,kernel 1128, services 1130 and/or drivers 1132). The libraries 1116 mayinclude system libraries 1134 (e.g., C standard library) that mayprovide functions such as memory allocation functions, stringmanipulation functions, mathematic functions, and the like. In addition,the libraries 1116 may include API libraries 1136 such as medialibraries (e.g., libraries to support presentation and manipulation ofvarious media format such as MPEG4, H.302, MP3, AAC, AMR, JPG, PNG),graphics libraries (e.g., an OpenGL framework that may be used to render2D and 9D in a graphic content on a display), database libraries (e.g.,SQLite that may provide various relational database functions), weblibraries (e.g., WebKit that may provide web browsing functionality),and the like. The libraries 1116 may also include a wide variety ofother libraries 1138 to provide many other APIs to the applications 1120and other software components/modules.

The frameworks 1118 (also sometimes referred to as middleware) mayprovide a higher-level common infrastructure that may be utilized by theapplications 1120 and/or other software components/modules. For example,the frameworks 1118 may provide various graphic user interface (GUI)functions, high-level resource management, high-level location services,and so forth. The frameworks 1118 may provide a broad spectrum of otherAPIs that may be utilized by the applications 1120 and/or other softwarecomponents/modules, some of which may be specific to a particularoperating system or platform.

The applications 1120 include built-in applications 1152 and/orthird-party applications 1154. Examples of representative built-inapplications 1152 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application, Third-party applications 1154 may include anyof the built-in applications 1152 as well as a broad assortment of otherapplications. In a specific example, the third-party application 1154(e.g., an application developed using the Android™ or iOS™ softwaredevelopment kit (SDK) by an entity other than the vendor of theparticular platform) may be mobile software running on a mobileoperating system such as iOS™, Android™, Windows® Phone, or other mobilecomputing device operating systems. In this example, the third-partyapplication 1154 may invoke the API calls 1124 provided by the mobileoperating system such as operating system 1114 to facilitatefunctionality described herein.

The applications 1120 may utilize built-in operating system functions(e.g., kernel 1128, services 1130 and/or drivers 1132), libraries (e.g.,system libraries 1134, API libraries 1136, and other libraries 1138),frameworks/middleware 1118 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systems,interactions with a user may occur through a presentation layer, such aspresentation layer 1122. In these systems, the application/module“logic” can be separated from the aspects of the application/module thatinteract with a user.

Some software architectures utilize virtual machines. For example,systems described herein may be executed utilizing one or more virtualmachines executed at one or more server computing machines. In theexample of FIG. 11 , this is illustrated by virtual machine 1140. Avirtual machine creates a software environment whereapplications/modules can execute as if they were executing on a hardwarecomputing device. A virtual machine 1140 is hosted by a host operatingsystem (operating system 1114) and typically, although not always, has avirtual machine monitor 1156, which manages the operation of the virtualmachine 1140 as well as the interface with the host operating system(i.e., operating system 1114). A software architecture executes withinthe virtual machine 1140 such as an operating system 1142, libraries1144, frameworks/middleware 1146, applications 1148 and/or presentationlayer 1150. These layers of software architecture executing within thevirtual machine 1140 can be the same as corresponding layers previouslydescribed or may be different.

FIG. 12 is a block diagram illustrating the computing device hardwarearchitecture 1200, within which a set or sequence of instructions can beexecuted to cause the machine to perform examples of any one of themethodologies discussed herein. For example, the architecture 1200 mayexecute the software architecture 1102 described with respect to FIG. 11. The architecture 1200 may operate as a standalone device or may beconnected (e.g., networked) to other machines. In a networkeddeployment, the architecture 1200 may operate in the capacity of eithera server or a client machine in server-client network environments, orit may act as a peer machine in peer-to-peer (or distributed) networkenvironments. The architecture 1200 can be implemented in a personalcomputer (PC), such as any of the server 102, the user devices 104 and110, a tablet PC, a hybrid tablet, a set-top box (STB), a personaldigital assistant (PDA), a mobile telephone, a web appliance, a networkrouter, switch or bridge, or any machine capable of executinginstructions (sequential or otherwise) that specify operations to betaken by that machine.

Example architecture 1200 includes a processor unit 1202 comprising atleast one processor (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU) or both, processor cores, compute nodes, etc.).The architecture 1200 may further comprise a main memory 1204 and astatic memory 1206, which communicate with each other via a link 1208(e.g., bus). The architecture 1200 can further include a video displayunit 1210, an alphanumeric input device 1212 (e.g., a keyboard), and auser interface (UI) navigation device 1214 (e.g., a mouse). In someexamples, the video display unit 1210, input device 1212 and UInavigation device 1214 are incorporated into a touch screen display. Thearchitecture 1200 may additionally include a storage device 1216 (e.g.,a drive unit), a signal generation device 1218 (e.g., a speaker), anetwork interface device 1220, and one or more sensors (not shown), suchas a global positioning system (GPS) sensor, compass, accelerometer, orother sensor.

In some examples, the processor unit 1202 or other suitable hardwarecomponent may support a hardware interrupt. In response to a hardwareinterrupt, the processor unit 1202 may pause its processing and executean interrupt service routine (ISR), for example, as described herein.

The storage device 1216 includes a machine-readable medium 1222 on whichis stored one or more sets of data structures and instructions 1224(e.g.; software) embodying or utilized by any one or more of themethodologies or functions described herein. The instructions 1224 canalso reside, completely or at least partially, within the main memory1204, static memory 1206, and/or within the processor unit 1202 duringexecution thereof by the architecture 1200, with the main memory 1204,static memory 1206, and the processor unit 1202 also constitutingmachine-readable media. Instructions 1224 stored at the machine-readablemedium 1222 may include, for example, instructions for implementing thesoftware architecture 1102, instructions for executing any of thefeatures described herein, etc.

While the machine-readable medium 1222 is illustrated in an example tobe a single medium, the term “machine-readable medium” can include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore instructions 1224. The term “machine-readable medium” shall also betaken to include any tangible medium that is capable of storing,encoding or carrying instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresent disclosure or that is capable of storing, encoding or carryingdata structures utilized by or associated with such instructions. Theterm “machine-readable medium” shall accordingly be taken to include,but not be limited to, solid-state memories, and optical and magneticmedia. Specific examples of machine-readable media include non-volatilememory, including, but not limited to, by way of example, semiconductormemory devices (e.g., electrically programmable read-only memory(EPROM), electrically erasable programmable read-only memory (EEPROM))and flash memory devices; magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 1224 can further be transmitted or received over thenetwork 106 using a transmission medium via the network interface device1220 utilizing any one of a number of well-known transfer protocols(e.g.; HTTP). Examples of communication networks include a local areanetwork (LAN), a wide area network (WAN), the Internet, mobile telephonenetworks, plain old telephone (POTS) networks, and wireless datanetworks (e.g., Wi-Fi, 3G, and 6G LTE/LTE-A or WiMAX networks). The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying instructions (e.g.,instructions 1224) for execution by the machine, and includes digital oranalog communications signals or other intangible medium to facilitatecommunication of such software.

Various components are described in the present disclosure as beingconfigured in a particular way. A component may be configured in anysuitable manner. For example, a component that is or that includes acomputing device may be configured with suitable software instructionsthat program the computing device. A component may also be configured byvirtue of its hardware arrangement or in any other suitable manner.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) can be used in combination with others. Otherembodiments can be used, such as by one of ordinary skill in the artupon reviewing the above description. The Abstract is to allow thereader to quickly ascertain the nature of the technical disclosure, forexample, to comply with 37C.F.R. § 1.72(b) in the United States ofAmerica. It is submitted with the understanding that it will not be usedto interpret or limit the scope or meaning of the claims.

Also, in the above Detailed Description, various features can be groupedtogether streamline the disclosure. However, the claims cannot set forthevery feature disclosed herein as embodiments can feature a subset ofsaid features. Further, embodiments can include fewer features thanthose disclosed in a particular example. Thus, the following claims arehereby incorporated into the Detailed Description, with a claim standingon its own as a separate embodiment. The scope of the embodimentsdisclosed herein is to be determined with reference to the appendedclaims, along with the full scope of equivalents to which such claimsare entitled.

The invention claimed is:
 1. A method comprising: reading, using aprocessor of a money dispensing machine, a quick response (QR) code froma recipient, the QR code including: a pre-authorized amount to bewithdrawn from an account associated with a user different from therecipient; and first image data, the first image data being captured viaan image capture device based on an interaction with a user interfacethat provides a selector to provide the first image data, wherein thefirst image data is provided after the selector is engaged in responseto a prompt being displayed to capture the first image data, the firstimage data being associated with a recipient intended to receive thepre-authorized amount where the first image data corresponds to an imageof the intended recipient, the intended recipient otherwise lackingaccess to the account associated with the user, wherein the QR code isgenerated when the first image data corresponding to the image of theintended recipient is received and the pre-authorized amount isreceived; in response to reading the QR code: capturing second imagedata associated with the recipient in response to reading the QR code atthe money dispensing machine via an image capture device at the moneydispensing machine; performing image analysis on the captured secondimage data associated with the recipient using one of signal processingduring digital image processing, image segmentation, or single particletracking; comparing the analyzed second captured image data associatedwith the recipient with the first image data associated with theintended recipient; determining if the recipient is the intendedrecipient based on the comparison; and providing the pre-authorizedamount to the recipient from the account associated with the user whenthe recipient is the intended recipient thereby allowing the recipientto directly withdraw the pre-authorized amount without access to theaccount associated with the user.
 2. The method of claim 1, furthercomprising: determining that the recipient is not the intended recipientbased on the comparison; and causing an alert to be sent to the userbased on determining that the recipient is not the intended recipient,wherein the alert includes the captured second image data and an optionto authorize the providing of the pre-authorized amount to therecipient.
 3. The method of claim 2, further comprising receiving anauthorization from the user to provide the pre-authorized amount to therecipient when a determination is made that the recipient is not theintended recipient based on the comparison.
 4. The method of claim 1,wherein the user is at a first location and the recipient is at a secondlocation remote from the first location and the recipient receives thepre-authorized amount from the account associated with the user at thesecond location when the user is at the first location separate from thesecond location.
 5. The method of claim 1, further comprising causing anacknowledgement to be sent to the user that includes the captured secondimage data of the recipient.
 6. The method of claim 1, wherein the QRcode expires when the pre-authorized amount is provided to therecipient.
 7. A non-transitory, machine-readable medium, comprisinginstructions, which when performed by a processor of a first computingdevice, causes the processor to perform operations to: read a quickresponse (QR) code from a recipient, the QR code including: apre-authorized amount to be withdrawn from an account associated with auser different from the recipient; and first image data, the first imagedata being captured via an image capture device based on an interactionwith a user interface that provides a selector to provide the firstimage data, wherein the first image data is provided after the selectoris engaged in response to a prompt being displayed to capture the firstimage data, the first image data being associated with a recipientintended to receive the pre-authorized amount where the first image datacorresponds to an image of the intended recipient, the intendedrecipient otherwise lacking access to the account associated with theuser, wherein the QR code is generated when the first image datacorresponding to the image of the intended recipient is received and thepre-authorized amount is received; in response to reading the QR code:capture second image data associated with the recipient in response toreading the QR code at the money dispensing machine via an image capturedevice at the money dispensing machine; perform image analysis on thecaptured second image data associated with the recipient using one ofsignal processing during digital image processing, image segmentation,or single particle tracking; compare the analyzed captured second imagedata associated with the recipient with the first image data associatedwith the intended recipient; determine if the recipient is the intendedrecipient based on the comparison; and provide the pre-authorized amountto the recipient from the account associated with the user when therecipient is the intended recipient thereby allowing the recipient todirectly withdraw the pre-authorized amount without access to theaccount associated with the user.
 8. The non-transitory,machine-readable medium of claim 7, wherein the instructions furthercause the processor to perform operations to: determine that therecipient is not the intended recipient based on the comparison; andcause an alert to be sent to the user based on determining that therecipient is not the intended recipient, wherein the alert includes thecaptured second image data and an option to authorize the providing ofthe pre-authorized amount to the recipient.
 9. The non-transitory,machine-readable medium of claim 8, wherein the instructions furthercause the processor to perform operations to receive an authorizationfrom the user to provide the pre-authorized amount to the recipient whena determination is made that the recipient is not the intended recipientbased on the comparison.
 10. The non-transitory, machine-readable mediumof claim 7, wherein the user is at a first location and the recipient isat a second location remote from the first location and the recipientreceives the pre-authorized amount from the account associated with theuser at the second location when the user is at the first locationseparate from the second location.
 11. The non-transitory,machine-readable medium of claim 7, wherein the instructions furthercause the processor to perform operations to cause an acknowledgement tobe sent to the user that includes the captured second image data of therecipient.
 12. The non-transitory, machine-readable medium of claim 7,wherein the QR code expires when the pre-authorized amount is providedto the recipient.
 13. A computing device comprising: processingcircuitry; and a memory device including instructions embodied thereon,wherein the instructions, which when executed by the processingcircuitry, configure the processing circuitry to perform operationsthat: read a quick response (QR) code from a recipient, the QR codeincluding: a pre-authorized amount to be withdrawn from an accountassociated with a user different from the recipient; and first imagedata, the first mage data being captured via an image capture devicebased on an interaction with a user interface that provides a selectorto provide the first image data, wherein the first image data isprovided after the selector is engaged in response to a prompt beingdisplayed to capture the first image data, the first image data beingassociated with a recipient intended to receive the pre-authorizedamount where the first image data corresponds to an image of theintended recipient; the intended recipient otherwise lacking access tothe account associated with the user, wherein the OR code is generatedwhen the first image data corresponding to the image of the intendedrecipient is received and the pre-authorized amount is received; inresponse to reading the QR code: capture second image data associatedwith the recipient in response to reading the QR code at the moneydispensing machine via an image capture device at the money dispensingmachine; perform image analysis on the captured second image dataassociated with the recipient using one of signal processing duringdigital image processing, image segmentation, or single particletracking; compare the analyzed captured second image data associatedwith the recipient with the first image data associated with theintended recipient; determine if the recipient is the intended recipientbased on the comparison; and provide the pre-authorized amount to therecipient from the account associated with the user when the recipientis the intended recipient thereby allowing the recipient to directlywithdraw the pre-authorized amount without access to the accountassociated with the user.
 14. The computing device of claim 13, whereinthe instructions further configure the processing circuitry to:determine that the recipient is not the intended recipient based on thecomparison; and cause an alert to be sent to the user based ondetermining that the recipient is not the intended recipient, whereinthe alert includes the captured second image data and an option toauthorize the providing of the pre-authorized amount to the recipient.15. The computing device of claim 14, wherein the instructions furtherconfigure the processing circuitry to receive an authorization from theuser to provide the pre-authorized amount to the recipient when adetermination is made that the recipient is not the intended recipientbased on the comparison.
 16. The computing device of claim 13, whereinthe user is at a first location and the recipient is at a secondlocation remote from the first location and the recipient receives thepre-authorized amount from the account associated with the user at thesecond location when the user is at the first location separate from thesecond location.
 17. The computing device of claim 13, wherein the QRcode expires when the pre-authorized amount is provided to therecipient.